-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated method for identifying devices by IPv4 address #139
Conversation
- Schema objects DeviceIpv4Addr and SingleIpv4Addr defined - Device property ipv4Address now of type DeviceIpv4Addr - CreateSession property devicePorts renamed deviceAllocatedPorts - Updated error message definitions - Minor format changes
Fix error message InvalidDevicePublicPortValue
Updated documentation for change in identifying devices by IPv4 address
Fixed error table numbering
Co-authored-by: Jose Luis Urien <[email protected]>
@hdamker , Observed IP address/Local IP address vs. Public IP address/Private IP address |
@emil-cheung Vote 1:
|
Yes, we prefer 'local' instead of 'assigned'. |
Replace oneOf with anyOf in DeviceIpv4Addr
@eric-murray As already written in the issues: Votes are created and open until next Thursday, May 4th, 12:00 UTC: |
- reverted deviceAllocatedPorts to devicePorts, but added description of modified usage - removed `format: ipv4` from SingleIpv4Addr
- Update documentation for devicePorts
- Fix InvalidDevicePortsRanges error decription
- Fix error camaraproject#9 description
- Fix CannotIdentifyDevice error
Ready for final review now |
- Renamed InsufficientProperties to InsufficientDeviceProperties - Renamed InconsistentProperties to InconsistentDeviceProperties - Fixed typo in PhoneNumber object description
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Co-authored-by: Ramesh Shanmugasundaram - Spry Fox Networks <[email protected]>
@hdamker I see that there will be a a lot of conflicts between this PR and the pending one I have to incorporate and update doc within spec, so I will wait to have this merged. If done in the next days I will submit mine before next meeting. |
Seems that we are good to go ... 3+ final reviews and 4 days no new comments. |
What type of PR is this?
What this PR does / why we need it:
This PR introduces the new schema
DeviceIpv4Addr
, which is used for theipv4Address
property of theDevice
object. TheDeviceIpv4Addr
object allows thedevice
to be identified by a combination of its public IPv4 address (publicAddress
) and at least one of either its public port (publicPort
) or private (device local) IPv4 address (privateAddress
).This modified schema is required to support the scenario where it is desired to identify the
device
by its private (local) IPv4 address, as this alone is generally insufficient to identify the device, and the public (NATed) IPv4 address must also be provided.Which issue(s) this PR fixes:
Fixes #34 : Resolving ueAddr ambiguity when it is the UE private address
Special notes for reviewers:
publicPort
is specified to identify thedevice
, this value is not used for flow rules. Description ofdevicePorts
has been added to clarify that these are the local ports used directly by the device for flow rules.Changelog input